MuleSoft Accelerator for Financial Services
Use case 6 - Salesforce org sync
Deliver a multi-org strategy faster with the Salesforce org sync use case.
Financial institutions are increasingly implementing a multi-Salesforce org strategy, which allows them to tailor the enterprise data strategies, back-end architecture, and governance structure for each business unit. This simplifies the configuration and management of org-wide settings and offers greater flexibility and speed for delivering enhancements. However, keeping data up to date across orgs is complex and time consuming.
Organizations need a solution that supports one-time and ongoing org synchronization so that financial institutions can have a complete and accurate view of their customers.
Ultimately, financial institutions will be able to better serve their customers and deliver innovations faster.
Overview
- Description
- Glossary
- Solution overview
- Assumptions and constraints
- High-level architecture
- Processing views
- Systems involved
See also
Description
This use case establishes the foundation for the Salesforce org to org synchronization process. Pre-built APIs and templates map Accounts and Contacts from Financial Services Cloud to Financial Services Cloud and from Financial Services Cloud to Sales Cloud and Service Cloud and vice versa.
Glossary
| Term | Definition |
|---|---|
| CIM | The Cloud Information Model for MuleSoft Accelerators defines a set of standard data structures that can be used as canonical representations of common entities for integrating systems. |
| FINS | Abbreviated term referring to the Financial and Insurance industries consisting of the Banking, Insurance and Wealth Management domains. |
| FSC | Salesforce Financial Services Cloud. Provides capabilities to support Banking, Insurance & Wealth and Asset Management sub-verticals. |
| Global Data | A Global Data service provides an accurate, consistent, and complete copy of business data for use by enterprise applications and business partners while also providing a means to link that copy to occurrences in other systems. |
| Org | Abbreviation for Salesforce Organization. A Salesforce org contains all of an organization’s data, processes and business functionality. |
Solution overview
The org sync solution enables organizations that have a multi-org strategy for their Salesforce instance to migrate data between their Salesforce orgs by enabling the creation and update of consistent and connected customer profiles across relevant applications, regardless of where the customer's journey starts. Salesforce Core data objects - accounts and contacts - can be connected from FSC to FSC and from Salesforce Core to FSC. Financial institutions need the ability to move data between Salesforce orgs to ensure customer service representatives have the most up to date data to support their customers.
Sync the following data objects in this order between FSC orgs:
- Contact objects
- Account objects
Sync the following data objects in this order between Salesforce Core and FSC orgs:
- Account objects
- Contact objects
Syncing occurs when the data change is noted.
Assumptions and constraints
- Organization is not yet syncing data between orgs.
- Organization has Sales Cloud, Service Cloud, or FSC.
- A MariaDB database will be used as the back end for the generic systems.
- The solution can be extended to use any salesforce cloud which support core objects.
Before you begin
|
The Getting Started with MuleSoft Accelerators guide provides general information on getting started with the accelerator components. This includes instructions on setting up your local workstation for configuring and deploying the applications. |
API-led diagram
Goals
- Provide an org migration solution for customers who take a multi-org approach to their Salesforce implementations.
- Support the creation of customer profiles across relevant applications.
- Support the creation of Global Customer ID & ID attribution.
- Orchestrate customer updates across designated applications.
Use case considerations
- A Global Data service will provide the golden copy of the customer profile.
Technical considerations
- Use CIM as the canonical model, where applicable (e.g., for Customers).
- Only core objects Account and Contact are part of the sync process.
High-level architecture
The following diagram represents the portion of the overall solution that pertains to the org to org sync use case.
Processing views
The diagrams below illustrate the processing sequences for the integrations and data synchronization activities included in this release.
Customer update sync
This activity diagram describes the process of synchronizing updates made to customers in any Salesforce Cloud to downstream systems.
Contact update sync
This activity diagram describes the process of synchronizing updates made to contacts in any Salesforce Cloud to downstream systems.
Systems involved
- Global Data (generic)
- Salesforce Financial Services Cloud
- Salesforce Sales Cloud
- Salesforce Service Cloud
Downloadable assets
Shared APIs (can be used across any use case)
- Accelerator MariaDB Global Party System API | API Specification | Implementation Template
- Accelerator Salesforce Customers System API | API Specification | Implementation Template
- Accelerator Customers Process API | API Specification | Implementation Template
- Accelerator Salesforce Customers Experience API | API Specification | Implementation Template
- Accelerator Salesforce Party Event Listener | Implementation Template
Custom components
- Cloud Information Model for MuleSoft Accelerators
- Accelerator Common Core | Source
- Accelerator POM Parent | Source
- FINS Common Resources | Source
- ID Graph Lightning Web Component | Source